Skip to content

Add Audit your Classic API dependencies guide - #6349

Draft
brentschaus-okta wants to merge 4 commits into
masterfrom
tbs-okta-1216283-audit-classic-api-dependencies
Draft

Add Audit your Classic API dependencies guide#6349
brentschaus-okta wants to merge 4 commits into
masterfrom
tbs-okta-1216283-audit-classic-api-dependencies

Conversation

@brentschaus-okta

@brentschaus-okta brentschaus-okta commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Description:

  • What's changed?
    Adds a new guide, Audit your Classic API dependencies, and cross-links it from the Classic Engine oriented docs that should point to it:
    • New guide at docs/guides/oie-upgrade-audit-classic-api-dependencies/: inventories Classic Engine authentication dependencies (the Classic Authentication API, the Factors API, the Sessions API, older self-hosted Sign-In Widgets, and Classic-era SDKs) that may still be running after an Identity Engine upgrade, and maps each one to the Identity Engine path that should replace it.
    • Registers the guide in docs/guides/index.md and adds a nav entry in navbar.const.js under the existing Okta Identity Engine upgrade section.
    • Cross-links the new guide from the OIE upgrade overview, the sign-in overview, the pre-upgrade integration discovery guide, the prepare-upgrade journey, and the sessions, API changes, sign-in widget, SDK, and MFA enrollment policy guides that map to specific Classic API rows in the new guide's dependency table.
    • Two forward references to sibling guides/journey pages that don't exist yet (part of the not-yet-scaffolded Modernize your sign-in and SSO flow with Okta Identity Engine journey, OKTA-1209649) are wrapped in TODO HTML comments, matching the pattern used in Align Plan embedded auth app upgrades guide with OIE modernization journey #6333, so they don't produce broken links.
    • Editorial pass on Understand authenticator enrollment policy API changes after the upgrade (oie-upgrade-mfa-enroll-policy): splits several run-on sentences, fixes two ungrammatical sentences, converts passive voice to active, and removes redundant wording. This was needed to clear the Acrolinx gate, which was blocking this PR at a score of 72 (minimum 80).
  • Is this PR related to a Monolith release? No.

Resolves:

Vercel Preview Link:

Preview link

New guide (OKTA-1216283) helps developers inventory Classic Engine
authentication dependencies (Authn API, Factors API, Sessions API,
older Sign-In Widgets, Classic-era SDKs) still running after an OIE
upgrade, and map each one to the supported Identity Engine path that
should replace it. Part of the Modernize your sign-in and SSO flow
with Okta Identity Engine journey (not yet published), registered
under the existing Okta Identity Engine upgrade nav section for now.

Co-Authored-By: Claude Code
Tightens prose in the new audit guide: converts remaining passive
voice to active, removes future-tense "should" in favor of present
tense, varies sentence length within paragraphs, and trims a few
sentences for concision.

Also links the new guide from the Classic Engine oriented docs that
should point to it: the OIE upgrade overview, sign-in overview, the
pre-upgrade integration discovery guide, the prepare-upgrade journey,
and the sessions, API changes, sign-in widget, SDK, and MFA enrollment
policy guides that map to specific Classic API rows in the new guide.

Co-Authored-By: Claude Code
Applies the same style pass used on the new Classic API dependencies
guide to this pre-existing doc, which was blocking the PR at an
Acrolinx score of 72 (minimum 80). Splits several run-on sentences
(one at 40 words, one at 37, one at 33), fixes two ungrammatical
sentences ("Whether you edit... when you click...", "Modify an
existing... to a factored one"), converts passive constructions to
active, removes redundant "you need to" and duplicate create-policy
explanations, and drops weak "The following are" openers.

Co-Authored-By: Claude Code
@okta okta deleted a comment from okta-prod-github-app Bot Jul 30, 2026
@okta okta deleted a comment from okta-prod-github-app Bot Jul 30, 2026
@okta-prod-github-app

Copy link
Copy Markdown

Acrolinx score

A minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Select Total score to review the Acrolinx scorecard for your article. Try to increase your individual scores, for example: Correctness. Your content will be clearer and more consistent.

Article Total score
Required:80
Word and phrases
(Brand, terms)
Preferred: 80
Correctness
(Spelling, grammar)
Preferred: 80
Clarity
(Readability)
Preferred: 80
Inclusive language
(+ accesibility)
Preferred: 80
packages/@okta/vuepress-site/docs/guides/index.md 87 67 80 78
packages/@okta/vuepress-site/docs/guides/oie-upgrade-api-changes/main/index.md 84 88 83 88
packages/@okta/vuepress-site/docs/guides/oie-upgrade-api-sdk-to-oie-sdk/main/index.md 91 100 92 79
packages/@okta/vuepress-site/docs/guides/oie-upgrade-audit-classic-api-dependencies/index.md 100 100 100 100
packages/@okta/vuepress-site/docs/guides/oie-upgrade-audit-classic-api-dependencies/main/index.md 82 87 71 85
packages/@okta/vuepress-site/docs/guides/oie-upgrade-identify-integrations/main/index.md 85 75 72 91
packages/@okta/vuepress-site/docs/guides/oie-upgrade-mfa-enroll-policy/main/index.md 75 29 86 53
packages/@okta/vuepress-site/docs/guides/oie-upgrade-overview/main/index.md 85 66 92 84
packages/@okta/vuepress-site/docs/guides/oie-upgrade-plan-embedded-upgrades/main/index.md 82 79 100 55
packages/@okta/vuepress-site/docs/guides/oie-upgrade-sessions-api/main/index.md 88 100 100 61
packages/@okta/vuepress-site/docs/guides/oie-upgrade-sign-in-widget/main/index.md 87 96 79 92
packages/@okta/vuepress-site/docs/guides/sign-in-overview/main/index.md 91 91 91 100
packages/@okta/vuepress-site/docs/journeys/OCI-prepare-upgrade-oie/main/index.md 85 66 83 100

Successfully checked 13 of 13 documents.
See summary in Content Analysis Dashboard

Reopen the pull request or push new changes to check again.

Depending on the Acrolinx server configuration, the
links expire after some time and you must have a login for the
Acrolinx server to access them again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants